
	BlueCielo Kronodoc 5.0 Administrator's Guide \| BlueCielo ECM Solutions

You are here: Appendix D: Oracle database configuration

Appendix D: Oracle database configuration

The Oracle database should be configured according to the following table. The three size classes Small, Medium, and Large are arbitrary, and are only provided as rough example estimates based on common cases.

The maximum size of the database with these settings is 32GB. More space can be allocated by adding more data files to the krono_data -tablespace.

	Small	Medium		Large
Database type:	OLTP, dedicated server mode
Features in use:	Server, Oracle Text
SGA size	512MB	1024MB	>2048MB
PGA size	170MB	340MB	>680MB
db_block_size	8192 bytes
Processes*	10	15	25
Space Management	File System
Database Character set:	AL32UTF8
Disk space for tablespaces	5GB	20GB	100GB
Tablespace krono_data	4GB	15GB	80GB (Requires multiple data files)
Tablespace krono_data	Locally managed, Automatic Space Management
Temporary tablespace	50MB	250MB	1GB
Temporary tablespace	Locally managed, Automatic Space Management
Undo tablespace	10MB	50MB		200MB
Redo logs	3 log groups, 20MB each	3 log groups, 20MB each		3 log groups, 20MB each

* The amount of processes is dependent on amount of users and amount of Kronodoc processes running on application server. There should be at least as many Oracle processes as Kronodoc server processes + a few spare processes for batch jobs

Other recommendations

Use Oracle Optimal Flexible Architecture and place the Oracle software installation and database files on dedicated file systems according to Oracle documentation.

Creating Kronodoc database user

The Kronodoc database user (e.g. krono) must be created with the following definitions:

Default tablespace krono_data
Quota unlimited on krono_data
Required privileges (e.g. via role krono_role):

Query rewrite
create view
create materialized view
ctxapp
connect
resource
create job